PSPNS-2655: Drop support for Half Duplex and 10MBit/s Mau Types for Profinet switch
Bugs:
PSPNS-2881: wrong error reported in case firmware is configured with incomplete database configuration
PSPNS-2879: SendAlarm service accepts requests with too little data in case of ProcessAlarm with USI 0x8320
PSPNS-2877: if MAC address is set via DPM Mailbox and NDIS-mode is used the MAC address is not shown in extended status block of second DPM channel
PSPNS-2875: In case of wrong usage of fix port configuration in engineering and IRT is used firmware may run in fatal error
PSPNS-2874: Wrong coding of AM_DeviceIdentification in asset management block
PSPNS-2873: wrong packet length reported in PNS_IF_AR_CHECK_IND
PSPNS-2872: sometimes under unclear circumstances the DCP Identify response generated contains an invalid Gateway address
PSPNS-2867: unexpected "remote mismatch diagnosis" generated in IRT operation mode
PSPNS-2865: Too restrictive IP network load filtering
PSPNS-2863: Invalid extension field value in second indication packet for fragmented response
PSPNS-2860: API Change: PNS_IF_GET_PARAMTER_REQ service for Parametertype PNS_IF_PARAM_PORT_STATISTIC does not return the parametertype in confirmation
PSPNS-2859: when using service PNS_IF_GET_PARAMETER_REQ its parameter ulAPI is not evaluated correctly (for some subtypes)
PSPNS-2858: APDU_Status.ProblemIndicator is not set even though a diagnosis is reported
PSPNS-2857: No configuration error reported even though nwid.nxd file is not found
PSPNS-2856: Firmware may crash when plugging a submodule during conection establishment
PSPNS-2851: Different values reported for Type Of Station by DCP protocol
PSPNS-2845: wrong FSHelloMode reported in case Controller uses strange FSU parameters
PSPNS-2836: No Check Indication when plugging a submodule into an AR
PSPNS-2830: SetOemPrmType 6 service to copy CycleCounter into DPM can not be used for DPM offset 0
PSPNS-2828: PNS_IF_SET_OEM_PARAMETER_REQ with ParameterType 9 (set I&M5 data) is rejected if used prior to PNS_IF_SET_CONFIGURATION_REQ
PSPNS-2824: inconsistent coding of remote NameOfStation when reading it in different access ways
PSPNS-2817: In some cases on connection abort not all unused check indications are generated
PSPNS-2815: Permanent stored Name of Station ignored when Set Firmware Parameter service used
PSPNS-2812: Unexpected upper case Name Of Station when using Set Firmware Parameter service
PSPNS-2810: Unexpected patching of internal variables on Set Configuration Service
PSPNS-2809: DPM Watchdog not working when configured by Ini-Batch
PSPNS-2868: add support for ProcessAlarms with UserStructureIdentifier 0x8320
Changes:
PSPNS-2871: Upgrade Hilscher TCP/IP stack to V2.5.0.1
Bugs:
PSPNS-2874: Wrong coding of AM_DeviceIdentification in asset management block
PSPNS-2873: wrong packet length reported in PNS_IF_AR_CHECK_IND
PSPNS-2872: sometimes under unclear circumstances the DCP Identify response generated contains an invalid Gateway address
PSPNS-2867: unexpected "remote mismatch diagnosis" generated in IRT operation mode
PSPNS-2865: Too restrictive IP network load filtering
PSPNS-2863: Invalid extension field value in second indication packet for fragmented response
PSPNS-2860: API Change: PNS_IF_GET_PARAMTER_REQ service for Parametertype PNS_IF_PARAM_PORT_STATISTIC does not return the parametertype in confirmation
PSPNS-2859: when using service PNS_IF_GET_PARAMETER_REQ its parameter ulAPI is not evaluated correctly (for some subtypes)
PSPNS-2858: APDU_Status.ProblemIndicator is not set even though a diagnosis is reported
PSPNS-2857: No configuration error reported even though nwid.nxd file is not found
PSPNS-2856: Firmware may crash when plugging a submodule during conection establishment
PSPNS-2781: Firmware crash when when reading asset management record object
PSPNS-2780: Fiberoptic media type not working properly on netX100 platform
PSPNS-2776: Unexpected GetAsset Indication generated in case many assets exist
PSPNS-2775: SPIRTA tests randomly failue due to Advanced Startup CPM monitoring
PSPNS-2774: in case IO Controller application negatively responds an alarm this information is not given to IO Device application
PSPNS-2770: Using TCPIP Packet API On second channel not possible
PSPNS-2769: unexpected SF LED behavior after ChannelInit in case application generated diagnosis exists
PSPNS-2768: NXIO firmware does not provide usedlibs.txt
PSPNS-2765: Service RCX_GET_DPM_IO_INFO_REQ returns unexpected values in case IOxS is active
PSPNS-2764: wrong Firmware Name given when reading Firmware Identification via DPM (limited firmware only)
PSPNS-2762: limited firmware does not respect all definitions in case time limit is reached
PSPNS-2761: DPM watchdog time is immediately modified when a SetConfiguration packet is received
PSPNS-2760: Configuration database with configuration for little endian byte order is no longer accepted by the firmware
PSPNS-2754: Re-plugging Submodule rejected with ERR_PNS_IF_DPM_ACCESS_WITH_INVALID_OFFSET
PSPNS-2753: Firmware may crash when receiving an invalid encoded RPC Read request
PSPNS-2746: wrong DPM communication channel size reported in Fileheader
PSPNS-2739: Sometimes RT Class 3 mismatch not reported as expected
PSPNS-2738: Disappearance of "Remote mismatch" releated diagnosis no reprted when "No Peer detected" diagnosis detected.
PSPNS-2737: Disappearance of "No Peer detected" diagnosis not reported when an other "Remote mismatch" releated diagnosis exists
PSPNS-2735: Wrong AlarmType used to report Sync mismatch and Fiber optic mismatch related diagnosis
PSPNS-2734: Add support for DCP Identify with MAC Address as filter
PSPNS-2724: After several runs of netload tests (faulty) in case of fragmented RPC Connect Request it may happen that the protocol stack is no longer reachable
PSPNS-2715: Wrong CMI/CPM connection monitoring in for legacy startup
PSPNS-2713: Wrong encoding of AM_Location field inside AssetManagment record object
PSPNS-2710: wrong ModuleIdentifier and SubmoduleIdentifier reported in Plug and Pull alarms
PSPNS-2708: User specific WriteRecord from network is not responded in case no application is registered at protocol stack and record is fragmented on network
PSPNS-2701: some error codes are not described in error header
PSPNS-2697: A read record of PE status contained in submodules not linked to an AR generates corrupted API numbers.
PSPNS-2696: Under some special circumstances Phy expected configuration not applied
PSPNS-2693: in case a SetConfig packet from AP task based on database is rejected by protocol stack the AP task does not set Ready bit
PSPNS-2689: After several Profinet connection establishments IP stack seems to stop working when NDIS is active
PSPNS-2688: Invalid answer generated for RCX_GET_DPM_IO_INFO_REQ in case only input data is configured
PSPNS-2687: In case application switches busstate to OFF no new error shall be reported to field ulCommunicationError
PSPNS-2686: missing packing directive for PROFIenergy ASE related services
PSPNS-2683: Set Configuration Request with invalid IOPS offsets is not detected
PSPNS-2680: [netX100/500 based firmware] Broadcast frames not indicated by Ethernet Interface
PSPNS-2671: [netX51]: NDIS interface not working as expected for Broadcast MAC address (indicated frames are shorter than they are on the real network)
PSPNS-2669: Some valid but unusual combinations of ChannelErrorType and ExtendedChannelErrorType are rejcted but should be accepted
PSPNS-2667: invalid error code returned when trying to read content of Diagnosis ASE or I&M data with partial access
PSPNS-2663: SPIRTA test "CMDEV_Legacy" fails if application delays ApplicationReady
PSPNS-2659: Unexpected behavior when reading record index 0x80A1
PSPNS-2657: Inconcistency for DCP suboption DeviceVendor between DCP Identify Response and DCP Get Response
PSPNS-2654: Wrong moduleID and submoduleID reported in Alarm ind of type Staus (ProfiEnergy Profile)
PSPNS-2646: under special netload conditions it may happen that protocol stack will never again answer to DCP IdentifyRequest frames (even if addressed)
PSPNS-2645: PNS_IF_GET_PARAM with PrmType 0x4 does not return internal diagnosis of PDEV submodules as expected
PSPNS-2643: SNMP may no longer work after receipt of DCP ResetFactorySettings while AR exists
PSPNS-2639: wrong SWRevPrefix used in I&M5 response in case firmware handles I&M data and I&M5 is active (certification issue)
PSPNS-2632: in case of application controlled startup LLDP frames are sent to early to network
PSPNS-2630: invalid versionnumber shown in usedlibs.txt for firmware files
PSPNS-2619: If a DA-AR is active and a second one is established the second one is rejected with wrong error code
PSPNS-2617: NXLOM example application does not handle DCP Reset to Factory as expected (Ceritification Issue)
PSPNS-2616: reconfiguration may return unexpected error indicating overlapping DPM offsets
PSPNS-2615: [netRAPID51]: NDIS functionality not available
PSPNS-2611: PNS_IF_GET_PARAMETER_REQ with PrmType 0x3 returns wrong PrmType in confirmation
PSPNS-2610: RPC Requests occasionally not responded
PSPNS-2609: unexpected NameOfStation applied when executing ChannelInit or SystemReset while using Sycon.net database configuration
PSPNS-2608: PNS_IF_GET_XMAC_DIAGNOSIS_REQ delivers some wrong values
PSPNS-2607: NameOfStation unexpectedly erased in case of database configuration
PSPNS-2605: notation of PROFINET in I&M5 annotation
PSPNS-2596: SetConfigurationRequest applies new DPM Watchdog values directly (without for Channel Init)
PSPNS-2592: unexpected LED behavior after ChannelInit while stack internal diagnosis exists
PSPNS-2746: wrong DPM communication channel size reported in Fileheader
PSPNS-2739: Sometimes RT Class 3 mismatch not reported as expected
PSPNS-2738: Disappearance of "Remote mismatch" releated diagnosis no reprted when "No Peer detected" diagnosis detected.
PSPNS-2737: Disappearance of "No Peer detected" diagnosis not reported when an other "Remote mismatch" releated diagnosis exists
PSPNS-2735: Wrong AlarmType used to report Sync mismatch and Fiber optic mismatch related diagnosis
PSPNS-2734: Add support for DCP Identify with MAC Address as filter
PSPNS-2724: After several runs of netload tests (faulty) in case of fragmented RPC Connect Request it may happen that the protocol stack is no longer reachable
PSPNS-2715: Wrong CMI/CPM connection monitoring in for legacy startup
PSPNS-2713: Wrong encoding of AM_Location field inside AssetManagment record object
PSPNS-2710: wrong ModuleIdentifier and SubmoduleIdentifier reported in Plug and Pull alarms
PSPNS-2708: User specific WriteRecord from network is not responded in case no application is registered at protocol stack and record is fragmented on network
PSPNS-2701: some error codes are not described in error header
PSPNS-2697: A read record of PE status contained in submodules not linked to an AR generates corrupted API numbers.
PSPNS-2696: Under some special circumstances Phy expected configuration not applied
PSPNS-2693: in case a SetConfig packet from AP task based on database is rejected by protocol stack the AP task does not set Ready bit
PSPNS-2689: After several Profinet connection establishments IP stack seems to stop working when NDIS is active
PSPNS-2688: Invalid answer generated for RCX_GET_DPM_IO_INFO_REQ in case only input data is configured
PSPNS-2687: In case application switches busstate to OFF no new error shall be reported to field ulCommunicationError
PSPNS-2686: missing packing directive for PROFIenergy ASE related services
PSPNS-2683: Set Configuration Request with invalid IOPS offsets is not detected
PSPNS-2680: [netX100/500 based firmware] Broadcast frames not indicated by Ethernet Interface
PSPNS-2671: [netX51]: NDIS interface not working as expected for Broadcast MAC address (indicated frames are shorter than they are on the real network)
PSPNS-2669: Some valid but unusual combinations of ChannelErrorType and ExtendedChannelErrorType are rejcted but should be accepted
PSPNS-2667: invalid error code returned when trying to read content of Diagnosis ASE or I&M data with partial access
PSPNS-2663: SPIRTA test "CMDEV_Legacy" fails if application delays ApplicationReady
PSPNS-2659: Unexpected behavior when reading record index 0x80A1
PSPNS-2657: Inconcistency for DCP suboption DeviceVendor between DCP Identify Response and DCP Get Response
PSPNS-2654: Wrong moduleID and submoduleID reported in Alarm ind of type Staus (ProfiEnergy Profile)
PSPNS-2646: under special netload conditions it may happen that protocol stack will never again answer to DCP IdentifyRequest frames (even if addressed)
PSPNS-2645: PNS_IF_GET_PARAM with PrmType 0x4 does not return internal diagnosis of PDEV submodules as expected
PSPNS-2643: SNMP may no longer work after receipt of DCP ResetFactorySettings while AR exists
PSPNS-2639: wrong SWRevPrefix used in I&M5 response in case firmware handles I&M data and I&M5 is active (certification issue)
PSPNS-2632: in case of application controlled startup LLDP frames are sent to early to network
PSPNS-2630: invalid versionnumber shown in usedlibs.txt for firmware files
PSPNS-2619: If a DA-AR is active and a second one is established the second one is rejected with wrong error code
PSPNS-2617: NXLOM example application does not handle DCP Reset to Factory as expected (Ceritification Issue)
PSPNS-2616: reconfiguration may return unexpected error indicating overlapping DPM offsets
PSPNS-2615: [netRAPID51]: NDIS functionality not available
PSPNS-2611: PNS_IF_GET_PARAMETER_REQ with PrmType 0x3 returns wrong PrmType in confirmation
PSPNS-2610: RPC Requests occasionally not responded
PSPNS-2609: unexpected NameOfStation applied when executing ChannelInit or SystemReset while using Sycon.net database configuration
PSPNS-2608: PNS_IF_GET_XMAC_DIAGNOSIS_REQ delivers some wrong values
PSPNS-2607: NameOfStation unexpectedly erased in case of database configuration
PSPNS-2605: notation of PROFINET in I&M5 annotation
PSPNS-2596: SetConfigurationRequest applies new DPM Watchdog values directly (without for Channel Init)
PSPNS-2592: unexpected LED behavior after ChannelInit while stack internal diagnosis exists
PSPNS-2739: Sometimes RT Class 3 mismatch not reported as expected
PSPNS-2738: Disappearance of "Remote mismatch" releated diagnosis no reprted when "No Peer detected" diagnosis detected.
PSPNS-2737: Disappearance of "No Peer detected" diagnosis not reported when an other "Remote mismatch" releated diagnosis exists
PSPNS-2735: Wrong AlarmType used to report Sync mismatch and Fiber optic mismatch related diagnosis
PSPNS-2734: Add support for DCP Identify with MAC Address as filter
PSPNS-2724: After several runs of netload tests (faulty) in case of fragmented RPC Connect Request it may happen that the protocol stack is no longer reachable
PSPNS-2680: [netX100/500 based firmware] Broadcast frames not indicated by Ethernet Interface
PSPNS-2671: [netX51]: NDIS interface not working as expected for Broadcast MAC address (indicated frames are shorter than they are on the real network)
PSPNS-2646: under special netload conditions it may happen that protocol stack will never again answer to DCP IdentifyRequest frames (even if addressed)
PSPNS-2645: PNS_IF_GET_PARAM with PrmType 0x4 does not return internal diagnosis of PDEV submodules as expected
PSPNS-2643: SNMP may no longer work after receipt of DCP ResetFactorySettings while AR exists
PSPNS-2534: Bus ON can unexpectedly be set when using netX Transport Driver to access the firmware
PSPNS-2526: in case application handles I&M data it is not possible to generate all required error codes in error situations
PSPNS-2524: some GSDML files violate GSD checking rules
PSPNS-2511: In case of ownership change directly after a new AR is established it may happen that IO Device rejects the submodule parameterization and aborts the AR
PSPNS-2428: Device related and AR related diagnosis-indexes deliver the same set of diagnosis
PSPNS-1118: Wrong hardware options on CIFX 104C-RE\F
PSPNS-2534: Bus ON can unexpectedly be set when using netX Transport Driver to access the firmware
PSPNS-2526: in case application handles I&M data it is not possible to generate all required error codes in error situations
PSPNS-2524: some GSDML files violate GSD checking rules
PSPNS-2511: In case of ownership change directly after a new AR is established it may happen that IO Device rejects the submodule parameterization and aborts the AR
PSPNS-1118: Wrong hardware options on CIFX 104C-RE\F